Add origin-apps plugin: build on the Origin API, port a GitHub App - #423

Wording only. Removes em dashes, connector colons, semicolon chains, and
passive voice; replaces "surface" with the concrete noun; one thought per
sentence. Rules and content unchanged. Plugin description is one new
identical string across the three manifests, both marketplace entries,
and the README row.

Co-authored-by: ali.nikseresht <ali.nikseresht@anysphere.co>

origin-api becomes a fetch-first list, a where-to-look table of
llms-full.txt anchors, four priority rules, and a short coming-from-GitHub
list for facts the docs do not carry yet. origin-isms rows point at docs
anchors instead of restating the idiom. spec-mapping drops copied paths
and slugs and the x-origin-webhook-resource extension, which the current
spec does not have; x-cursor-visibility is corrected to a field badge.
brief-template's mirror rule and hello-world mechanics defer to the docs.
gap-bar and README drop a feedback address the docs do not name.

Co-authored-by: ali.nikseresht <ali.nikseresht@anysphere.co>

The docs now carry coming-from-github, ids, preview, and the x-origin-*
summary, so the in-skill Coming from GitHub list becomes a pointer, ID
form points at #ids, PREVIEW points at #preview without claiming where the
badge appears, and the subscription and pageSize rules defer to #events
and #pagination.

Co-authored-by: ali.nikseresht <ali.nikseresht@anysphere.co>

The docs will not carry a coming-from-github section, so origin-api
points at the porting skill in one line and origin-isms rows name the
Origin answer or its docs anchor directly. The payload-field rule lives in
the porting mapping step and points at the per-field notes under
#event-payloads.

Co-authored-by: ali.nikseresht <ali.nikseresht@anysphere.co>

The docs render every webhook payload family and every endpoint's
response fields with nested objects expanded to dotted paths, deeper
than the script's two-level expansion, so the script and its PyYAML
requirement go. spec-mapping points the REST and payload-field steps at
the matching llms-full.txt headings. origin-api gains a lookup-order rule
(llms.txt first, one section for a narrow question, full files only for
broad work); the porting skill inherits it.

Co-authored-by: ali.nikseresht <ali.nikseresht@anysphere.co>

Manifests lose the porting and integration keywords and tags.
spec-mapping's payload outcomes now include "present in the envelope" so
GitHub's action field maps to event.type instead of falling through to
the gap bar, matching the brief template's five How values. The porting
skill's out-of-scope line says the team sends the cards.

Co-authored-by: ali.nikseresht <ali.nikseresht@anysphere.co>

The brief's section is Feedback for Cursor with Feedback: entries; the
reference is the feedback bar and format. The gap parity label stays: a
gap row produces a feedback entry. Section 7 is scoped to decisions the
team must make so it does not duplicate section 6.

Co-authored-by: ali.nikseresht <ali.nikseresht@anysphere.co>

brief-template.md describes what a good brief does and offers a default
outline the agent adapts or skips, with a small app's brief fitting one
screen. Fixed question lists, column counts, and boilerplate sections are
gone; what remains is what makes the brief trustworthy: evidence for app
claims, Origin claims resolved against the fetched docs, feedback free of
partner internals. unknown folds into not-available; same and reshaped
fold into maps; the four marks are optional vocabulary. Feedback for
Cursor stays last and is also written to ORIGIN-FEEDBACK.md when there is
at least one entry.

Co-authored-by: ali.nikseresht <ali.nikseresht@anysphere.co>

Every docs pointer becomes reference/<anchor>.md under the Origin docs
base URL. origin-api's lookup rule is llms.txt first, then the one page;
llms-full.txt and openapi.yaml stay for broad work. The field-map steps
fetch the endpoint's or payload family's own page, with rg over
llms-full.txt kept as the broad-run fallback.

Co-authored-by: ali.nikseresht <ali.nikseresht@anysphere.co>

Pointers become quoted section headings resolved through llms.txt at run
time, so the skill does not depend on a docs deploy order and survives
renamed anchors. The base URL stays for llms.txt, llms-full.txt, and
openapi.yaml.

Co-authored-by: ali.nikseresht <ali.nikseresht@anysphere.co>

Folds discovery, spec-mapping, gap-bar, origin-isms, and brief-template
into the porting SKILL.md plus one reference (brief, feedback bar, crib);
the eval scored this shape level with the longer one. Also from the eval:
the mirror rule states facts (merging and default-branch changes are
native-only; on a GitHub-sourced mirror every event except
repository.pushed arrives and calls beyond metadata and contents reads
return 403); brevity is structural (list only what does not map straight
across, payload fields only when absent or a follow-up read, a word
budget by app size); a three-line filter sits before feedback; the stale
user-OAuth item points at "Acting on behalf of users" and names the
user-token permission probe as a workaround; ORIGIN-FEEDBACK.md carries no
license header, repo or product name, or other forge, and docs
contradictions go to Cursor.

Co-authored-by: ali.nikseresht <ali.nikseresht@anysphere.co>

Wording only. "Crib" becomes "Where GitHub features live on Origin";
"the bar", "first-run path", "marks", "provenance", "fan-out", "rows",
"call families", and "payload family" become ordinary words; native
repositories and stable outbound mirrors are explained once in plain terms;
optional table labels are plain words. Rules, eval fixes, and the
section-name pointers are unchanged.

Co-authored-by: ali.nikseresht <ali.nikseresht@anysphere.co>

openapi.yaml and llms-full.txt are about 870 KB and 575 KB, roughly 350k
tokens together, more than a context window holds. Both skills now say to
curl them to disk and rg them, reading only the matching sections. Narrow
questions still go through llms.txt to the one section.

Co-authored-by: ali.nikseresht <ali.nikseresht@anysphere.co>

Replaces the curl and rg commands with tool-neutral intent (save locally,
search for the heading or annotation, read the matching part) and keeps
the concrete search targets. Saved copies go in a temporary location
outside the app's repository, so a download cannot overwrite or litter the
working tree.

Co-authored-by: ali.nikseresht <ali.nikseresht@anysphere.co>